home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Magnum One
/
Magnum One (Mid-American Digital) (Disc Manufacturing).iso
/
d19
/
pcbnet28.arc
/
PCBNET.DOC
< prev
next >
Wrap
Text File
|
1991-05-01
|
7KB
|
159 lines
PCBoard 14.5 Net Scan Conference Mail Waiting Flags Program
Description: This program will update Mail Waiting flags for specific
users who have mail waiting in any conference. This program
should be used for EchoMail type conferences (Although you
can use it whenever you want).
WHY Use It: If you are like me and carry Echo Mail Conferences (ILink,
MetroLink, PCRelay, FidoNet, etc.) most of the software
out there will not update the Mail Waiting Flags for your
Users when they have mail. This program *WILL* do it and
it is VERY FAST.
WHAT Happens: After you run PCBNet, and it finds a user in your NDX files,
it will update the Mail Waiting Flags both in the USERS and
USERS.INF file for each specific conference.
When the user logs onto your BBS they will be notified that
they have MAIL WAITING in that specific conference. Is nice
to know if you finally got that message to a reply.
VERY IMPORTANT: Please Read
----------------------------------------------------------------------------
1) Be sure you use the /INIT parameter to properly setup everything. If
you don't, strange things can happen and will probably cause you
heartache. I've done everything I can to avoid such things, but
all machines seem to work differently because of configurations.
2) When you have been using PCBNet for a while and you ADD or DELETE
conferences, you will need to use the /INIT option BEFORE running your
EVENT for Echo Mail. The PCBNET.NET file is created in your directory
where you run PCBNET.EXE (Unless you use the /NET option).
----------------------------------------------------------------------------
In order to properly use this program you *MUST* pass at least one
command line switches to it:
The command line switches look like this:
/INIT Use for First time Initialization on PCBNet 2.2.
If you were using a previous version of PCBNet
you NEED to use this option for proper option. Use
this switch on FIRST TIME INITIALIZATION or when
ADDING or DELETING CONFERENCES!
/C:l-h l means LOW conference number, h means HIGH conference
number.
** /ASEC:xx;xx-xx This means ACCEPTABLE Security Levels that PCBNet should
be flagging users for Mail. A RANGE of security
levels can be specified (i.e. /ASEC:0;5;10-20;60-70;75).
Anybody with these security levels will be flagged as
having mail (If any found for them). This is an OPTION!
If you use this switch, the /USEC CANNOT be used!
** /USEC:xx;xx-xx This means UNACCEPTABLE Security levels that PCBNet
should NOT be flagging users for mail. Anybody whose
security level is in this switch will NOT be flagged
as having mail (If any found for them). A range of
security levels can be specified (i.e. /USEC:10-20;50)
Anybody with these security levels will not be flagged
as having mail PERIOD. This is an OPTION!
If you use the /USEC switch, the /ASEC CANNOT be used!
/NET:path/name example would be: /NET:C:\UTILS\PCBNET\PCBNET.NET
* Note1: The PCBNET.NET file is 4 byte times the number of conferences
(Plus the main board) in file length.
** Note2: Please note that the /ASEC and /USEC gives you the option of
selecting users to be flagged for mail or users not to be flagged
for mail. You can only use ONE of these switches. Let me give
you an example. I my own BBS that I run I have TWO security
levels for LOCAL users. It benefits me more to use the /ASEC
switch since all I have to do is enter in two security levels
like this:
PCBNet /C:1-138 /ASEC:15;25
In this example only Users with a security level of 15 or 25
would be flagged as having mail in the echo mail conferences while
anybody else would not.
Now someone who has various Local security levels and only one
or two Long Distance (Levels 60 and 61) security levels would
benefit from the /USEC switch like this:
PCBNet /C:0-200 /USEC:60-61
In this example any of the long distance callers with a security
level of 60 and 61 would NOT have their mail waiting flags updated
while any other security level would.
Both of these switches are OPTIONS and are not necessary. Use
your own judgement wisely!
Valid Examples:
FIRST TIME INITIALIZATION
-------------------------
PCBNet /INIT /C:200-300 - This would create the proper PCBNET file and
then would scan all conferences starting with
LOW message number.
USE THESE AFTER FIRST TIME INITIALIZATION
-----------------------------------------
PCBNet /C:1-2000 - Would Scan Conferences 1 - 2000 Updating Mail
Waiting Flags if mail hasn't been read.
PCBNet /C:5-20 - Would Scan Conferences 5 - 20 Updating Mail
Waiting Flags if mail hasn't been read.
PCBNet /C:1-200 /USEC:50 - Would Scan Conferences 1 - 200 Updating Mail
Waiting Flags for ALL users EXCEPT Anyone with a
Security Level of 50.
PCBNet /C:1-200 /ASEC:20-25;50;55-58
- Would Scan Conferences 1 - 200 Updating Mail
Waiting Flags for Users with a Security Level of
20,21,22,23,24,25,50,55,56,57,58.
INVALID EXAMPLES:
PCBNet /C:1 (Needs a High Number Also)
PCBNet /C:50-4 (Must start with a Low Number and then a High
Number)
PCBNet /C:1-20;50-100 (You can only pass ONE Low and ONE High Number)
PCBNet /C:1-20 /ASEC:10 /USEC:20
(You can only use ONE of the Two /ASEC or /USEC
switches
What directory do you run it from?
PCBNet *MUST* be run from a directory that contains your PCBOARD.DAT file
and in most cases, you use this program in an EVENT (Except for first time
inialization).
First Time Initialization:
For first time initialization, you should be running it from the DOS Prompt
(In other words, you should monitor it). Simply type in:
1) PCBNet /INIT [option /NET:path/filename]
Event Running:
Once you have used the first time initialization, you should append this
example to your EVENT.SYS file:
C:
CD \PCB
PCBNet /c:l-h
etc..
Hopefully these documents are a little better. If you are having problems,
please leave a comment on Salt Air to Cam DeBuck (Salt Air Support Staff).